Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated for Current API situation #2706

Merged
merged 1 commit into from
Aug 4, 2016
Merged

Updated for Current API situation #2706

merged 1 commit into from
Aug 4, 2016

Conversation

ynoTL23
Copy link
Contributor

@ynoTL23 ynoTL23 commented Aug 4, 2016

I updated the README in accordance to the current API situation with PokeStops.

Please feel free to reword/rephrase/add if there is anything I missed.

I updated the README in accordance to the current API situation with PokeStops.

Please feel free to reword/rephrase/add if there is anything I missed.
@thepeople03
Copy link

does that means the bot is working now? :)

@Nbsloc
Copy link

Nbsloc commented Aug 4, 2016

Nah , mine still doesn't work :(

@Jordano3710
Copy link

Na doesnt work for me either man

@mschader
Copy link

mschader commented Aug 4, 2016

This just means, that when this will be submitted, the front page here will kindly inform you about the status of the bot and gives you a reddit link with an explanation why it is not working.

@petrskuta
Copy link

No, it is not working.

@Bekareth
Copy link

Bekareth commented Aug 4, 2016

The issue was found by Mila432 : link

@romeoDo
Copy link

romeoDo commented Aug 4, 2016

OMG!!, Read the update please. He stated clearly that the bot won't work (for now). Nothing was updated in the bot program.

@Sharke
Copy link

Sharke commented Aug 4, 2016

Rofl. I love how people are asking "does this mean it works now" when all this change is more stating of the obvious that it doesn't work.

@ultimatescarz
Copy link

sorry to sound like an ass but when one see updated it desperate people sees this it looks like hey I have updated the bot they dont read the whole sentence or they dont want to understand... unfortunately its like Dig Bick when you read fast it becomes you know what..

@Sharke
Copy link

Sharke commented Aug 4, 2016

@ultimatescarz Point taken. I read Dig Bick wrong probably 5 times. But still people should take a deep breath and just be patient.

@Bushrouter
Copy link

Bushrouter commented Aug 4, 2016

Hi! I just wondering is it possible to produce by easy correction of the current program code a stable positioning? Just put a character nearby the certain point and let him/her wait for a beast and catch it?
According to the present message of the programme the issue is pokestops location. Does the possibility to catch pets still available? In a case if trainer has enough p-balls this algorithm could work anyhow...

@baldmonkey1
Copy link

i hope the programmers find a way out ;-;

@hilycker
Copy link
Contributor

hilycker commented Aug 4, 2016

@Bushrouter the issue is with pokemon too

@BornSupercharged BornSupercharged merged commit 2ac24f0 into NecronomiconCoding:master Aug 4, 2016
@droped
Copy link

droped commented Aug 4, 2016

Are you guys stupid enough to not know what THE FUCKING REAME.MD IS??? It doesn't change anything is relation to the program's code. Even if it did, you guys would have to compile it yourselves and clearly you would never be able to since you think a mere pull request without an app update can actually do something. Here: https://www.reddit.com/r/pokemongodev/comments/4w1cvr/pokemongo_current_api_status/d63g28s

Until pogo devs figure the new api thingy, there won't be any bots (location spoof may still work, try it out maybe). If the program doesn't update, don't bother waiting to see if it will find pokestops because it won't.

@Nick2400
Copy link

Nick2400 commented Aug 4, 2016

Since location spoofing still works, woudn't it be an idea to disable looking for pokestops and pokemon and just walk around and change the incubators everytime. Logically this should be able to work since my location spoofing on my phone still works. This way we would still be able to breed eggs.

@droped
Copy link

droped commented Aug 4, 2016

@Nick2400 That could risk a ban so it is better not to do it.

@gianlu696
Copy link

how much time we have to wait for the bot?

@droped
Copy link

droped commented Aug 4, 2016

@gianlu696 Forever. Now wait.

@ynoTL23 ynoTL23 deleted the patch-1 branch August 4, 2016 19:28
schnapster pushed a commit to schnapster/NecroBot that referenced this pull request Dec 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.